SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 42943: The triggering transaction debit amounts in the Alert Details screen of SAS® Anti-Money Laundering are expressed as whole numbers.

DetailsAboutRate It
In the Alert Details screen, the triggering transaction debit amounts are expressed as whole numbers. There are no fractional numbers displayed in these amounts. This issue only occurs for sites using Teradata as the database.

The issue is caused by the null place-holder for the debit column in the first part of the query below (for credit transactions) specifying the type as INT (integer). This INT type is then assumed for the debit column in each of the joined parts of the query. As a result, the DECIMAL(15,5) values are converted to INT resulting in the fraction truncation.
sasaml.alerttrans.triggering.transactions= SELECT ... 'Credit', a.currency_amount as credit, (cast(NULL as int)) as debit, ... UNION SELECT ... 'Debit', (cast(NULL as int)) AS credit, b.currency_amount AS debit, ...
That the first reference to the debit column is typed as an INT, this apparently carries forwards to the subsequent debit column references.

This also occurs when no type is specified; it behaves as it defaults to INT.

The issue can be resolved by specifying DECIMAL(15,5) as the type for the place-holder debit column reference instead of INT. As long as the first reference to the debit column is defined as DECIMAL(15,5), any subsequent casting the place-holder as INT have no effect. However, for consistency, all should be changed.

Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Anti-Money LaunderingMicrosoft® Windows® for 64-Bit Itanium-based Systems2.2.15.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition2.2.15.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition2.2.15.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows XP 64-bit Edition2.2.15.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows 2000 Advanced Server2.2.19.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server2.2.19.1 TS1M3 SP4
Microsoft Windows 2000 Server2.2.19.1 TS1M3 SP4
Microsoft Windows 2000 Professional2.2.19.1 TS1M3 SP4
Microsoft Windows NT Workstation2.2.19.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter Edition2.2.15.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition2.2.15.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows Server 2003 Standard Edition2.2.15.19.1 TS1M3 SP49.3 TS1M0
Microsoft Windows XP Professional2.2.15.19.1 TS1M3 SP49.3 TS1M0
Windows Vista2.2.15.19.1 TS1M3 SP49.3 TS1M0
Windows Vista for x642.2.15.19.1 TS1M3 SP49.3 TS1M0
64-bit Enabled AIX2.2.15.19.1 TS1M3 SP49.3 TS1M0
64-bit Enabled HP-UX2.2.15.19.1 TS1M3 SP49.3 TS1M0
64-bit Enabled Solaris2.2.15.19.1 TS1M3 SP49.3 TS1M0
HP-UX IPF2.2.15.19.1 TS1M3 SP49.3 TS1M0
Linux2.2.15.19.1 TS1M3 SP49.3 TS1M0
Solaris for x642.2.15.19.1 TS1M3 SP49.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.